Atari Mega Archive 1/Atari Mega Archive - Volume 1.iso/program/rcs5ap1s.lzh/README

Text File | 1991-01-03 | 12KB | 278 lines

/* Copyright (C) 1982, 1988, 1989 Walter Tichy
   Copyright 1990 by Paul Eggert
   Distributed under license by the Free Software Foundation, Inc.

This file is part of RCS.

RCS is free software; you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation; either version 1, or (at your option)
any later version.

RCS is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
GNU General Public License for more details.

You should have received a copy of the GNU General Public License
along with RCS; see the file COPYING.  If not, write to
the Free Software Foundation, 675 Mass Ave, Cambridge, MA 02139, USA.

Report problems and direct all questions to:

    [e-mail]

*/

$Id: README,v 5.6 1990/12/13 06:54:04 eggert Exp $

This directory contains complete sources for RCS version 5.5.


Installation notes:

  RCS requires a diff that supports the -n option.
  Get GNU diff (version 1.15 or later) if your diff lacks -n.

  RCS works best with a diff that supports -a, -L, and (diff3 only) -m.
  GNU diff supports these options.

  Sources for RCS are in the src directory.
  Read the directions in src/Makefile to set up the options
  for building RCS on your system.
  If `make' fails to build src/conf.h, look in src/conf.error
  to see what went wrong in the src/conf.sh shell file.
  If all else fails, create src/conf.h manually by editing a
  copy of src/conf.heg.

  Manual entries reside in man.

  To test your installation of RCS, run the shell file src/rcstest.

  Troff source for the paper `RCS--A System for Version Control', which
  appeared in _Software--Practice & Experience_, is in rcs.ms.


RCS compatibility notes:

  RCS version 5 reads RCS files written by any RCS version released since 1982.
  It also writes RCS files that these older versions of RCS can read,
  unless you use one of the following new features:

    checkin times after 1999/12/31 23:59:59 GMT
    checking in non-text files
    non-Ascii symbolic names
    rcs -bX, where X is nonempty
    rcs -kX, where X is not `kv'
    RCS files that exceed hardcoded limits in older RCS versions


Features new to RCS version 5 include:

  RCS can check in arbitrary files, not just text files, if diff -a works.
  RCS can merge lines containing just a single `.' if diff3 -m works.
  GNU diff supports the -a and -m options.

  RCS can now be installed as a setgid or setuid program
  if the setegid() and seteuid() system calls work.
  Setid privileges yield extra security if RCS files are protected so that
  only the effective group or user can write RCS directories.
  RCS uses the real group and user for all accesses other than to RCS files.
  On older hosts lacking setegid() and seteuid(), RCS uses the effective group
  and user for all accesses; formerly it was inconsistent.

  New options to co, rcsdiff, and rcsmerge give more flexibility to keyword
  substitution.

    -kkv substitutes the default `$Keyword: value $' for keyword strings.
    However, a locker's name is inserted only as a file is being locked,
    i.e. by `ci -l' and `co -l'.  This is normally the default.

    -kkvl acts like -kkv, except that a locker's name is always inserted
    if the given revision is currently locked.  This was the default in
    version 4.  It is now the default only with when using rcsdiff to
    compare a revision to a working file whose mode is that of a file
    checked out for changes.

    -kk substitutes just `$Keyword$', which helps to ignore keyword values
    when comparing revisions.

    -ko retrieves the old revision's keyword string, thus bypassing keyword
    substitution.

    -kv retrieves just `value'.  This can ease the use of keyword values, but
    it is dangerous because it causes RCS to lose track of where the keywords
    are, so for safety the owner write permission of the working file is
    turned off when -kv is used; to edit the file later, check it out again
    without -kv.

  rcs -ko sets the default keyword substitution to be in the style of co -ko,
  and similarly for the other -k options.  This can be useful with binary file
  formats that cannot tolerate changing the lengths of keyword strings.
  However it also renders a RCS file readable only by RCS version 5 or later.
  Use rcs -kkv to restore the usual default substitution.

  RCS can now be used by development groups that span timezone boundaries.
  All times are now displayed in GMT, and GMT is the default timezone.
  To use local time with co -d, append ` LT' to the time.
  When interchanging RCS files with sites running older versions of RCS,
  users may encounter discrepancies of up to 13 hours in old time stamps.
  The list of timezone names has been modernized.

  Dates are now displayed using four-digit years, not two-digit years.
  Years given in -d options must now have four digits.
  This change is required for RCS to continue to work after 1999/12/31.
  The form of dates in version 5 RCS files will not change until 2000/01/01,
  so in the meantime RCS files can still be interchanged with sites
  running older versions of RCS.  To make room for the longer dates,
  rlog now outputs `lines: +A -D' instead of `lines added/del: A/D'.

  To help prevent diff programs that are broken or have run out of memory
  from trashing an RCS file, ci now checks diff output more carefully.

  ci -k now handles the Log keyword, so that checking in a file
  with -k does not normally alter the file's contents.

  RCS no longer outputs white space at the ends of lines
  unless the original working file had it.
  For consistency with other keywords,
  a space, not a tab, is now output after `$Log:'.
  Rlog now puts lockers and symbolic names on separate lines in the output
  to avoid generating lines that are too long.
  A similar fix has been made to lists in the RCS files themselves.

  RCS no longer outputs the string `Locker: ' when expanding Header or Id
  keywords.  This saves space and reverts back to version 3 behavior.

  The default branch is not put into the RCS file unless it is nonempty.
  Therefore, files generated by RCS version 5 can be read by RCS version 3
  unless they use the default branch feature introduced in version 4.
  This fixes a compatibility problem introduced by version 4.

  RCS can now emulate older versions of RCS; see `co -V'.
  This may be useful to overcome compatibility problems
  due to the above changes.

  Programs like Emacs can now interact with RCS commands via a pipe:
  the new -I option causes ci, co, and rcs to run interactively,
  even if standard input is not a terminal.
  These commands now accept multiple inputs from stdin separated by `.' lines.

  ci now silently ignores the -t option if the RCS file already exists.
  This simplifies some shell scripts and improves security in setuid sites.

  Descriptive text may be given directly in an argument of the form -t-string.

  The character set for symbolic names has been upgraded
  from Ascii to ISO 8859.

  rcsdiff now passes through all options used by GNU diff;
  this is a longer list than 4.3BSD diff.

  merge's new -L option gives tags for merge's overlap report lines.
  This ability used to be present in a different, undocumented form;
  the new form is chosen for compatibility with GNU diff3's -L option.

  rcsmerge and merge now have a -q option, just like their siblings do.

  RCS now attempts to ignore parts of an RCS file that look like they come
  from a future version of RCS.

  When properly configured, RCS now strictly conforms with Posix 1003.1-1988.
  Normally, RCS file names contain `,', which is outside the Posix portable
  filename character set; but in impoverished Posix environments, you can
  compile RCS so that the RCS file for Foo is named just RCS/Foo.
  RCS can still be compiled in non-Posix traditional Unix environme